Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0955

reference
327-tree-1
name
0955
tree-preservation-order

undefined

327-tpo-1
uprn
address-text
point
POINT (-1.018221 50.866855)
geometry
MULTIPOLYGON (((-1.018150 50.866848,-1.018153 50.866861,-1.018163 50.866874,-1.018178 50.866884,-1.018198 50.866891,-1.018220 50.866893,-1.018242 50.866891,-1.018262 50.866885,-1.018278 50.866875,-1.018288 50.866863,-1.018292 50.866849,-1.018289 50.866835,-1.018279 50.866822,-1.018263 50.866812,-1.018244 50.866806,-1.018222 50.866803,-1.018200 50.866805,-1.018180 50.866811,-1.018164 50.866821,-1.018154 50.866834,-1.018150 50.866848)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL